Setting up C Make Support attributes

In the Project Tree of the Project Editor, checkmark

pico.shared , lib.shared , MSWIN.shared on Windows and UNIX.shared on Unix.
Choose Project > Attributes of Checkmarked Projects....
The Attributes of Checkmarked Projects dialog appears. You can use this dialog to set/ modify the attributes of multiple projects at the same time.
In the Attributes of Checkmarked Projects dialog
Setting up Make Support for pico.shared

Under the Build Options node, select Project Targets.
Make sure that pico is highlighted in the Project List.
In the Executable field of the Ansi C/C++ tab, enter

pico on Unix and pico.exe on Windows. This will be the name of the project's executable.
Under the Build Options node, select Directives.
Select the checkbox to the right of the Generate button and press Set for All.
This attribute is now set for all projects.
Under the Build Options node, select Build Structure.
In Recursive Make Dirs field, enter lib.
In order to build the project's executable, SNiFF+ must first build the target of the lib.shared subproject (a library). SNiFF+ uses the project information in Recursive Make Dirs field to determine the order in which to execute Make.
Setting up Make Support for lib.shared

Highlight lib in the Project List.
Under the Build Options node, select Project Targets.
In the Library field of the of the Ansi C/C++ tab, enter

libpico.a . This will be the name of the library built in this project.
Under the Build Options node, select Build Structure.
From the Passed to Superproject drop-down, choose Library.
The project's library is exported to pico.shared and is used to build the Pico executable.
In Recursive Make Dirs field, enter UNIX/MSWIN on Unix/Windows.
The library is built using objects built in the platform-specific subdirectory of lib.shared .
Setting up Make Support for MSWIN.shared (Windows only)

Highlight MSWIN in the Project List.
Under the Build Options node, select Project Targets.
In the Relinkable Object field of the of the Ansi C/C++ tab, enter

osdep.o . This will be the name of the relinkable object built in this project.
Press Ok to apply the changes to the project attributes.
A dialog appears asking you if you want to update Makefiles. You will be updating Makefiles later on, so press No.
Setting up Make Support for UNIX.shared (Unix only)

Highlight UNIX in the Project List.
Under the Build Options node, select Project Targets.
In the Relinkable Object field of the of the Ansi C/C++ tab, enter

osdep.o . This will be the name of the relinkable object built in this project.
Press Ok to apply the changes to the project attributes.
A dialog appears asking you if you want to update Makefiles. You will be updating Makefiles later on, so press No.
Saving changes

- In the Launch Pad, save the changes made to

pico.shared and its subprojects:

- Select

pico.shared in the Project List.
- Choose Project > Save Project pico.shared.
- In the Alert dialog that appears, press the Save all button.
  What's next
  You may think that the next step is to build the project's executable in the SSWE. It isn't. In SNiFF+'s working environments concept, SSWEs contain only shared source code, and SOWEs contain the objects and targets based on this code.
  During project setup, you created a SNiFF+ project in the directory that contains your team's shared source code, i.e., in the SSWE. Once the project has been created, the only time you open it in the SSWE is to update it. For any real development work, open the project in a PWE.
  So, the next step is to check in the project (its Project Description File) and its source files into the Repository. When the process is over, all the files in the SSWE will be read-only.
  Then, you can open the project in the SOWE and build the executable in it. This task is covered in First Build in the SOWE.